System and method for generating data regarding a vehicle crash

ABSTRACT

A method includes receiving initial sensor data and additional sensor data; and generating combined sensor data. A computing device for includes one or more processors; and one or more memories coupled to the one or more processors, the one or more memories including non-transitory computer executable instructions stored therein that, when executed by the one or more processors, cause the one or more processors to: receive initial sensor data and additional sensor data; and generate combined sensor data. A computer readable storage medium includes non-transitory computer readable instructions stored thereon for generating data regarding a vehicle crash, wherein the instructions when executed on one or more processors cause the one or more processors to: receive initial sensor data and additional sensor data; and generate combined sensor data.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of U.S. application Ser. No.16/949,097 entitled “System and Method for Generating Data Regarding aVehicle Crash,” filed Oct. 13, 2020. application Ser. No. 16/949,097 isa continuation of U.S. application Ser. No. 15/199,156, entitled “Systemand Method for Generating Data Regarding a Vehicle Crash,” filed Jun.30, 2016, issued as U.S. Pat. No. 10,832,504; and which claims priorityto U.S. Provisional Patent Application No. 62/326,408, entitled “Systemand Method for Generating Data Regarding a Vehicle Crash,” filed on Apr.22, 2016, the disclosure of which is hereby incorporated herein byreference.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to vehicle crash data and, moreparticularly, to a system and method for generating data regarding avehicle crash.

BACKGROUND

A vehicle may include one or more sensors that may be a part of acomputing device or operate in conjunction with a computing device tofacilitate crash detection when the vehicle is traveling. In some cases,the computing device may be a smart phone and the one or more sensorsmay operate in conjunction with an app installed and executing on thesmart phone to facilitate crash detection. However, current uses ofsensors and apps to detect vehicle crashes have several drawbacks.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

In one aspect, a computer-implemented method for generating dataregarding a vehicle crash includes: (i) receiving, using one or moreprocessors of a mobile computing device within a vehicle, initial sensordata indicating that a vehicle crash has occurred, and additional sensordata for a first amount of time; and (ii) generating, using the one ormore processors, combined sensor data that includes first sensor datacorresponding to a period of time before the crash of the vehicle andsecond sensor data corresponding to a period of time after the crash ofthe vehicle.

In another aspect, a computing device for generating data regarding avehicle crash includes one or more processors; and one or more memoriescoupled to the one or more processors, the one or more memoriesincluding non-transitory computer executable instructions stored thereinthat, when executed by the one or more processors, cause the one or moreprocessors to: (i) receive initial sensor data via the one or moreprocessors indicating that a vehicle crash has occurred, and additionalsensor data for a first amount of time; and (ii) generate, using the oneor more processors, combined sensor data that includes first sensor datacorresponding to a period of time before the crash of the vehicle andsecond sensor data corresponding to a period of time after the crash ofthe vehicle.

In yet another aspect, a computer readable storage medium includesnon-transitory computer readable instructions stored thereon forgenerating data regarding a vehicle crash, wherein the instructions whenexecuted on one or more processors cause the one or more processors to:(i) receive initial sensor data via the one or more processorsindicating that a vehicle crash has occurred, and additional sensor datafor a first amount of time; and (ii) generate, using the one or moreprocessors, combined sensor data that includes first sensor datacorresponding to a period of time before the crash of the vehicle andsecond sensor data corresponding to a period of time after the crash ofthe vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

The figures described below depict various aspects of the system andmethods disclosed herein. It should be understood that each figuredepicts an embodiment of a particular aspect of the disclosed system andmethods, and that each of the figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingfigures, in which features depicted in multiple figures are designatedwith consistent reference numerals.

FIG. 1 illustrates an example system for generating vehicle crash data;

FIG. 2 illustrates an example computing device that may be animplementation of one or more computing devices described elsewhereherein, and illustrates components thereof;

FIG. 3 is a flow chart of an example method, routine, or process forgenerating an indication of whether a vehicle crash has occurred;

FIG. 4 is a flow chart of an example method, routine, or process forproviding post-crash information after an indication that a vehiclecrash has occurred;

FIG. 5 illustrates the example system of FIG. 1 for generating vehiclecrash data in greater detail;

FIG. 6 is a flow chart of an example method, routine, or process forgenerating vehicle crash data;

FIG. 7 is a flow chart of another example method, routine, or processfor generating vehicle crash data;

FIG. 8 illustrates an implementation of the example computing device ofFIG. 2 and components thereof that may be used in generating dataregarding a vehicle crash; and

FIG. 9 is a flow chart of an example method, routine, or process forgenerating data regarding a vehicle crash.

The figures depict various aspects of the present invention for purposesof illustration only. One skilled in the art will readily recognize fromthe following discussion that alternative embodiments of the structuresand methods illustrated herein may be employed without departing fromthe principles of the invention described herein.

DETAILED DESCRIPTION

Although the following text sets forth a detailed description ofnumerous different embodiments, it should be understood that the legalscope of the description is defined by the words of the claims set forthat the end of this patent and equivalents. The detailed description isto be construed as exemplary only and does not describe every possibleembodiment since describing every possible embodiment would beimpractical. Numerous alternative embodiments could be implemented,using either current technology or technology developed after the filingdate of this patent, which would still fall within the scope of theclaims.

It should also be understood that, unless a term is expressly defined inthis patent using the sentence “As used herein, the term ‘______’ ishereby defined to mean . . . ” or a similar sentence, there is no intentto limit the meaning of that term, either expressly or by implication,beyond its plain or ordinary meaning, and such term should not beinterpreted to be limited in scope based on any statement made in anysection of this patent (other than the language of the claims). To theextent that any term recited in the claims at the end of this patent isreferred to in this patent in a manner consistent with a single meaning,that is done for sake of clarity only so as to not confuse the reader,and it is not intended that such claim term be limited, by implicationor otherwise, to that single meaning. Finally, unless a claim element isdefined by reciting the word “means” and a function without the recitalof any structure, it is not intended that the scope of any claim elementbe interpreted based on the application of 35 U.S.C. § 112(f).

I. Example System and Related Functionality

FIG. 1 illustrates an example system 100 for generating vehicle crashdata, such as an indication of whether a vehicle crash has occurred. Theexample system 100 may include a vehicle 102 (only a portion of which isshown in FIG. 1 for ease of illustration and explanation), a computernetwork 104, a remote computing device(s) 106, a database 108 or otherdata storage mechanism (e.g., one or more hard disk drives, opticalstorage drives, solid state storage devices, etc.), and call managementdevice(s) 110. As shown in FIG. 1 and described in further detail below,each of the vehicle 102, the remote computing device(s) 106, thedatabase 108, and the call management device(s) 110 may becommunicatively coupled to the computer network 104. In otherembodiments, various ones of the elements of the example system 100 maybe communicatively coupled to one another in a manner other than via thecomputer network 104. By way of example, the remote computing device(s)106 may be directly coupled to the call management device(s) 110 througha dedicated wired or wireless link (as shown in FIG. 1), and/or may bedirectly coupled to the database 108 through a dedicated wired orwireless link (not shown in FIG. 1). As in other examples shown anddescribed herein, singular and/or plural instances of various elementsmay be shown and described as such for ease of illustration andexplanation. Thus, for example, the example system 100 may include anumber of vehicles 102 with parties therein that are insured by aninsurance provider, and any suitable number of remote computingdevice(s) 106, databases 108, and call management device(s) 110.

The computer network 104 may be a computer network of an insuranceprovider (e.g., provided or used by the insurance provider, orcommunications over which the insurance provider otherwise controls orfacilitates). In various embodiments, as further described below,processors of the remote computing device(s) 106, the call managementdevice(s) 110, and/or devices in the vehicle 102 may executeinstructions to transmit data to, receive data from, or otherwisecommunicate with one another and/or the database 108, for example, viathe computer network 104. The computer network 104 may be or may includea network such as the Internet and/or any other type of suitable network(e.g., a local area network (LAN), a metropolitan area network (MAN), awide area network (WAN), a mobile network, a wired or wireless network,a private network, a virtual private network, etc.). The computernetwork 104 may also or alternatively be or include one or more cellularnetworks such as code division multiple access (CDMA) network, GSM(Global System for Mobile Communications) network, WiMAX (WorldwideInteroperability for Microwave Access) network, Long Term Evolution(LTE) network, etc.

As shown in the example system 100, the vehicle 102 includes a driver112 seated in a driver seat 114 and associated with (e.g., owning and/orpossessing) a first mobile computing device 116, such as a smart phone.The vehicle 102 may also include a front passenger 118 seated in a frontpassenger seat 120 and associated with a second mobile computing device122, such as another smart phone. While various examples herein describecomputing devices such as the first mobile computing device 116 and/orthe second mobile computing device 122 as smart phones, it will beunderstood by one of ordinary skill in the art in light of the teachingand disclosure herein that each of the computing devices referred toherein may be any suitable computing device. For example, each of thecomputing devices referred to herein may be implemented as a desktopcomputer, a laptop computer, a mobile phone such as a smart phone, atablet, a phablet, smart glasses, other wearable computing device(s),etc.

As further described below, the remote computing device(s) 106 (e.g., aninsurance provider server(s)) and/or a device(s) in the vehicle 102,such as the first mobile computing device 116 and/or the second mobilecomputing device 122, may be used in generating an indication of whethera vehicle crash has occurred, such as a crash of the vehicle 102. Invarious embodiments, as further described below, the first mobilecomputing device 116 and/or the second mobile computing device 122, forexample, may include one or more sensors that may output sensor dataindicative of whether a crash of the vehicle 102 has occurred. Forexample, each of the first mobile computing device 116 and the secondmobile computing device 122 may include one or more of an accelerometer,a pressure sensor (e.g., a barometric pressure sensor), a gyroscope, amagnetometer, or a sound monitoring component (e.g., a microphone orother suitable sound monitoring component). In some embodiments, asfurther described below, the one or more sensors may output sensor dataindicating that a condition corresponding to a crash of the vehicle 102has occurred (e.g., indicating that an amount of accelerationcorresponding to a crash of the vehicle 102 has been sensed), andfurther sensor data may then be output and used to generate anindication of whether the crash of the vehicle 102 has occurred.

The first mobile computing device 116, the second mobile computingdevice 122, and/or the remote computing device(s) 106 may also oralternatively be used in generating, for example, an indication of aseverity of the crash of the vehicle 102, a location of the vehicle 102at a time of the crash of the vehicle 102, the time of the crash of thevehicle 102, a speed of the vehicle 102 at the time of the crash of thevehicle 102, a number of occupants of the vehicle 102 at the time of thecrash of the vehicle 102, and/or a Delta-V associated with the crash ofthe vehicle 102, as further described below. Such data regarding thecrash of the vehicle 102 may be provided to and/or used by the insuranceprovider (e.g., at the call management device(s) 110), where theinsurance provider may provide insurance coverage with respect to thevehicle 102 and an insured party or parties (e.g., a user(s) of thefirst mobile computing device 116 and/or the second mobile computingdevice 122, such as the driver 112 and/or the front passenger 118), asfurther described herein. In some embodiments, such data regarding thecrash of the vehicle 102 may be stored in the database 108 for retrievalby, for example, the remote computing device(s) 106 when, for example,an insured party calls the insurance provider to initiate a claimassociated with the crash, electronically initiates a claim with theinsurance provider, etc.

The call management device(s) 110 may include any suitable device ordevices at, for example, a call center (e.g., claim center) of theinsurance provider to receive, place, and otherwise process telephonecalls, for example. For example, the call management device(s) 110 mayinclude one or more telephones; one or more computing devicescommunicatively coupled to the telephones and, for example,communicatively coupled to the computer network 104 and/or the remotecomputing device(s) 106; etc. As such, an incoming call to the insuranceprovider (e.g., to initiate a claim associated with a crash of thevehicle 102) may be received and processed using the call managementdevice(s) 110 in conjunction with, for example, information received atthe call management device(s) 110 from the remote computing device(s)106, as further described below.

Still further, as also further described below, the first mobilecomputing device 116 and/or the second mobile computing device 122, forexample, may be used in generating sensor data (e.g., from one or moresensors included in the first mobile computing device 116 and/or thesecond mobile computing device 122, as described above) corresponding toa period of time before the crash of the vehicle 102 and sensor datacorresponding to a period of time after the crash of the vehicle 102.The sensor data corresponding to the periods of time before and afterthe crash of the vehicle 102 may be collected by a buffer(s) of thefirst mobile computing device 116 and/or the second mobile computingdevice 122, and may then be stored in additional data storage of thefirst mobile computing device 116 and/or the second mobile computingdevice 122.

As further discussed below, one or more additional mobile computingdevices may be present in the vehicle 102 (e.g., in rear seats of thevehicle 102, as further discussed with respect to, for example, FIG. 5),and may be used in performing actions such as those described above anddiscussed in further detail below. Moreover, while mobile computingdevices such as the first mobile computing device 116 and the secondmobile computing device 122 are shown and described as being associatedwith (e.g., possessed by a user sitting in) particular seats of thevehicle 102, the various computing devices described herein may havedifferent associations with seats of the vehicle 102; may not beassociated with any particular seat; one or more seats may not have anassociated computing device; etc.

II. Example Computing Device

FIG. 2 illustrates an example computing device 150 and componentsthereof. An instance or instances of the computing device 150, orportions thereof, may be an implementation(s) of, for example, one ormore of one or more of the remote computing device(s) 106, one or moreof the call management device(s) 110, the first mobile computing device116, or the second mobile computing device 122. The computing device 150may include sensors, such as when the computing device 150 is animplementation of the first mobile computing device 116 or the secondmobile computing device 122. More particularly, the sensors may include,for example, a gyroscope 152, a pressure sensor 154 (e.g., a barometricpressure sensor), a sound monitoring component 156 (e.g., a microphone),a magnetic sensor 158 (e.g., a magnetometer), and an accelerometer 160.As with other components shown in the figures and described herein, anysuitable number of each of the sensors 152-160 may be included in aparticular implementation of one of the computing devices describedherein, and/or one or more of the sensors 152-160 may be omitted in aparticular implementation of one of the computing devices describedherein.

The computing device 150 may include a controller 162. The controller162 may include a program memory 164, a microcontroller or amicroprocessor 166, a memory 168, and an input/output (I/O) circuit 170,all of which may be interconnected via an address/data bus 172. Theprogram memory 164 may store computer-executable instructions, which maybe executed by the microprocessor 166. The memory 168 may include one ormore forms of volatile and/or non-volatile, fixed and/or removablememory, such as read-only memory (ROM), electronic programmableread-only memory (EPROM), random access memory (RAM), erasableelectronic programmable read-only memory (EEPROM), and/or other harddrives, flash memory, MicroSD cards, and/or other suitable form(s) ofmemory.

It should be appreciated that although FIG. 2 depicts only onemicroprocessor 166, the controller 162 may include multiplemicroprocessors 166. Similarly, the program memory 164 of the controller162 may include additional RAM(s) 174 and multiple program memories176A, 176B and/or 176C (or any suitable number of multiple programmemories) storing one or more corresponding modules, routines, and/orinstructions, etc. used in, for example, generating vehicle crash data,according to the particular configuration of the controller 162 and thecomputing device 150. Additionally, although FIG. 2 depicts the I/Ocircuit 170 as a single block, the I/O circuit 170 may include a numberof different types of I/O circuits (not depicted). The RAM(s) 174 andthe program memory/memories 176A, 176B and/or 176C may be implemented inany known form of non-transitory computer readable storage media,including but not limited to semiconductor memories, magneticallyreadable memories, and/or optically readable memories. It should also beappreciated that the computing device 150 may include additional, fewer,or alternate components, such as depending on a particular devicedescribed herein of which the computing device 150 is an implementation.

III. Example Method for Generating Indication of Whether Vehicle CrashHas Occurred

FIG. 3 is a flow chart of an example method, routine, or process 200 forgenerating an indication of whether a vehicle crash has occurred, suchas a crash of the vehicle 102. One or more processors, which may be oneor more processors of the first mobile computing device 116, such as amicroprocessor(s) implemented as described above with respect to FIG. 2,may determine whether base sensor data output by one or more basesensors of a mobile computing device indicates that a conditioncorresponding to a crash of the vehicle 102 has occurred (block 202).The mobile computing device may be, for example, the first mobilecomputing device 116, and the one or more processors (which may be oneor more processors of the first mobile computing device 116, as notedabove) may perform the determination described with respect to block 202by receiving base sensor data from the base sensor(s) of the firstmobile computing device 116 when the first mobile computing device 116is present within the vehicle 102. For example, the first mobilecomputing device 116 may be a smart phone of, or otherwise possessed byor in the control of, the driver 112. In another embodiment, the one ormore processors may be one or more processors of the second mobilecomputing device 122, and/or the mobile computing device including thebase sensor(s) may be the second mobile computing device 122.

The one or more processors may perform the actions described withrespect to block 202, and the actions described with respect to otherblocks herein, by executing computer-executable instructions stored in,for example, one or more program memories such as the program memories176A, 176B, and/or 176C when the computing device 150 is animplementation of a mobile computing device that includes the one ormore processors and one or more program memories. Thecomputer-executable instructions executed by the one or more processorsto perform actions described herein may constitute, for example, one ormore smart phone apps used for crash detection and post-crash actions asfurther discussed below. Such an app(s) may be provided by the insuranceprovider and made available to a user (e.g., insured party) for downloadto the first mobile computing device 116

With further reference to the actions described with respect to block202, in one embodiment, the one or more base sensors may include theaccelerometer 160, and the base sensor data may be or may includeacceleration data output by the accelerometer 160. The determination ofwhether the base sensor data output by the one or more base sensorsindicates that a condition corresponding to a crash of the vehicle 102has occurred may be or may include a determination of whether an amountof acceleration indicated by the accelerometer 160 is at least a certainnumber of “g”s. For example, if the amount of acceleration indicated bythe accelerometer 160 is equal to or greater than such a certain numberor threshold number of “g”s, such an indication by the accelerometer 160may be an indication of a condition corresponding to a crash of thevehicle 102, because the vehicle 102 may be more likely to experience ahigh magnitude of acceleration (e.g., a sudden stop) in the event of acrash.

With continued reference to the actions described with respect to block202, a suitable sensor or sensors other than or in addition to theaccelerometer 160 may be or may be included in the one or more basesensors and may output the base sensor data or a portion(s) thereof. Asjust one example, the gyroscope 152 may be included in the basesensor(s), and an output from the gyroscope 152 that is equal to orgreater than a predetermined number of radians per second may indicatethat a condition corresponding to a crash of the vehicle 102 hasoccurred, for example.

If it is determined with respect to block 202 that the base sensor dataindicates that a condition corresponding to a crash of the vehicle 102has not occurred, the example method, routine, or process 200 may remainat the determination described with respect to block 202 until it isdetermined that the base sensor data indicates that a conditioncorresponding to a crash of the vehicle 102 has occurred.

If it is determined that the base sensor data indicates that a conditioncorresponding to a crash of the vehicle 102 has occurred, the one ormore processors (e.g., one or more processors of the first mobilecomputing device 116, as described above) may cause at least oneadditional sensor of the mobile computing device (e.g., the first mobilecomputing device 116) to begin outputting additional sensor data (block204). For example, where the base sensor(s) is the accelerometer 160,the one or more processors may cause one or more of the gyroscope 152,the pressure sensor 154, the magnetic sensor 156, or the soundmonitoring component 158 to turn on or otherwise activate or beginoperation, and thereby begin outputting additional sensor data. In thismanner, the accelerometer 160 or other suitable base sensor(s) mayadvantageously be used to determine whether a condition corresponding toa crash of the vehicle 102 has occurred without having to use allsensors of the mobile computing device (e.g., the first mobile computingdevice 116). When such a condition (e.g., which may correspond toparticular output(s) of the base sensor(s) as discussed above) hasoccurred, the additional sensor(s) may be caused to output theadditional sensor data in order to increase the accuracy of anindication of whether a crash of the vehicle 102 has occurred, with suchan indication being further discussed below.

For example, the additional sensor(s) may increase the accuracy of anindication of whether a crash has occurred by providing additional data,and/or by providing data where the base sensor(s) may not be able toprovide sufficiently accurate outputs. As one example, where the basesensor(s) includes the accelerometer 160, the accelerometer 160 may insome mobile computing devices, such as the first mobile computing device116, be limited in the number of “g”s that can be detected and outputtedby the accelerometer 160. Accordingly, use of the additional sensor(s)in such an example may improve the accuracy of an indication of whethera crash has occurred. It will be appreciated in light of the teachingand disclosure herein that power consumption by, for example, the firstmobile computing device 116 may advantageously be reduced by notoperating the additional sensor(s) unless a condition corresponding to acrash has occurred.

The one or more processors may cause the at least one additional sensorof the first mobile computing device 116 (or other suitable mobilecomputing device, as discussed herein) to output the additional sensordata for an amount of time (e.g., a predetermined amount of time) afterthe at least one additional sensor begins outputting the additionalsensor data (block 206). The amount of time may be, for example, apredetermined amount of time that corresponds to an expected duration ofa crash of the vehicle 102. For example, the insurance provider may havedetermined that a typical vehicle crash has a duration of less thanthree-tenths of a second, and the app used to perform actions describedherein (such an app being discussed above) may thus cause the firstmobile computing device 116, and more particularly the one or moreprocessors thereof, to cause the at least one additional sensor tooutput the additional sensor data for three-tenths of a second. It willbe appreciated any other suitable time may be used as the amount of timeduring which the at least one additional sensor is caused to output theadditional sensor data, and that the app may be configured (e.g., by theinsurance provider) accordingly.

The one or more processors may receive an indication from at least asecond mobile computing device (e.g., the second mobile computing device122 and/or an additional mobile computing device(s) such as one of theadditional mobile computing device(s) further discussed with respect toFIG. 5) of whether the crash of the vehicle 102 has occurred, where theat least the second mobile computing device may be located within thevehicle 102 (block 208). The indication from the at least the secondmobile computing device of whether the crash of the vehicle 102 hasoccurred may be determined by the at least the second mobile computingdevice in any suitable manner. In some embodiments, the indication fromthe at least the second mobile computing device of whether the crash ofthe vehicle 102 has occurred may be or may include further sensor datafrom at least one sensor of the at least the second mobile computingdevice. For example, at least one sensor of the at least the secondmobile computing device, such as at least one sensor of one of the typesof sensors 152-160 shown and described with respect to FIG. 2, mayoutput sensor data that may indicate whether a crash of the vehicle 102has occurred, and this sensor data may be received using the one or moreprocessors of the first mobile computing device 116.

The sensor data received from the at least the second mobile computingdevice using the one or more processors of the first mobile computingdevice 116 may, for example, be used in conjunction with the base sensordata and the additional sensor data described above to generate anindication of whether the crash of the vehicle 102 has occurred, asfurther described below. In some embodiments, the sensor data receivedfrom the at least the second mobile computing device may include atleast second base sensor data and/or at least second additional sensordata. The at least second base sensor data and/or the at least secondadditional sensor data may be received, for example, where one or moreof the at least the second mobile computing device uses a base sensor(s)to determine whether a condition corresponding to a crash of the vehicle102 has occurred and uses an additional sensor(s) to output additionalsensor data in a manner similar to that described with respect to thefirst mobile computing device 116.

With continued reference to the actions described with respect to block208, in another example, one or more processors of the at least thesecond mobile computing device may perform actions similar to thosedescribed above with respect to blocks 202, 204, and 206, and mayanalyze resulting base sensor data and additional sensor data output bysensors of the at least the second mobile computing device. The one ormore processors of the at least the second mobile computing device maythus determine the indication that is received using the one or moreprocessors of the first mobile computing device 116, as described withrespect to block 208, based on an analysis of such sensor data from theat least the second mobile computing device. In this example, theindication received as described with respect to block 208 may notinclude all or a portion of such sensor data from the at least thesecond mobile computing device, but instead may include data resultingfrom an analysis of such sensor data.

In a further example, the one or more processors of the at least thesecond mobile computing device may analyze sensor data from any suitablesensor or sensors, such as the sensors shown and described with respectto FIG. 2, in order to determine the indication from the at least thesecond mobile computing device of whether the crash of the vehicle 102has occurred. In such an example, the at least the second mobilecomputing device need not use one or more base sensors and need notcause at least one additional sensor to begin outputting additionalsensor data in the same manner as described with respect to the firstmobile computing device 116. For example, the one or more processors ofthe at least the second mobile computing device may cause any suitablesensor or sensors of the at least the second mobile computing device(such as one or more of the types of sensors 152-160) to operateconcurrently and to output sensor data that may be analyzed to determinethe indication from the at least the second mobile computing device ofwhether the crash of the vehicle 102 has occurred.

The one or more processors may generate an indication of whether thecrash of the vehicle 102 has occurred (block 210). In variousembodiments, the one or more processors may generate the indication ofwhether the crash of the vehicle 102 has occurred based on one or moreof the additional sensor data caused to be outputted as described withrespect to blocks 204 and 206; the base sensor data; the indication fromthe at least the second mobile computing device of whether the crash ofthe vehicle 102 has occurred; a geographic location(s) of each of thefirst mobile computing device 116 and/or the at least the second mobilecomputing device; and/or any other suitable factors. For example, theindication of whether the crash has occurred may be based on factorssuch as whether the additional sensor data includes an output of thegyroscope 152 that is more than a particular (e.g., predetermined)number of radians per second; whether the additional sensor dataincludes a change in an output of the pressure sensor 154 that is morethan a particular number of millibars; whether the additional sensordata includes a change in an output of the sound monitoring component156 that is more than a particular number of decibels; whether theadditional sensor data includes a change in an output of the magneticsensor 158 that is more than a particular amount; and/or any othersuitable factor(s).

When the indication of whether the crash of the vehicle 102 has occurredis an indication that the crash of the vehicle 102 has occurred, anotification and/or prompt may be displayed to a user of the firstmobile computing device 116 and/or to a user(s) of the at least thesecond mobile computing device (e.g., a user(s) of the second mobilecomputing device 122 and/or an additional mobile computing device(s)such as those discussed with respect to FIG. 5), as further discussedbelow. When the indication of whether the crash of the vehicle 102 hasoccurred is an indication that the crash of the vehicle 102 has notoccurred, the one or more processors may cause the app to, for example,adjust the manner of analysis of the base sensor data so as to prevent“false alarms” in which the base sensor data indicates a conditioncorresponding to a crash when a crash has not actually occurred. Forexample, the one or more processors may implement a machine learningprocess and/or other suitable techniques to make such an adjustment(s).Additionally or alternatively, when the indication of whether the crashof the vehicle 102 has occurred is an indication that the crash of thevehicle 102 has not occurred, the one or more processors may cause theapp to, for example, adjust the manner of analysis of the base and/oradditional sensor data from the base and/or additional sensors of thefirst mobile computing device 116 in conjunction with sensor data fromthe at least the second mobile computing device, such as by way of amachine learning process.

The one or more processors may generate at least one of an indication ofa severity of the crash of the vehicle 102, an indication of a locationof the vehicle 102 at a time of the crash of the vehicle, an indicationof the time of the crash of the vehicle 102, an indication of a speed ofthe vehicle 102 at the time of the crash, or an indication of a Delta-Vassociated with the crash of the vehicle 102 (block 212). Theindication(s) generated as described with respect to block 212 may begenerated based on, for example, the base sensor data output by the atleast one base sensor of the first mobile computing device 116 and/orbased on, for example, the additional sensor data output by the at leastone additional sensor of the first mobile computing device 116. In someembodiments, the indication(s) generated as described with respect toblock 212 may be generated further based on, for example, theaforementioned indication from the at least the second mobile computingdevice of whether the crash of the vehicle 102 has occurred (whichindication may be or include, for example, sensor data or anothersuitable indication as described above with respect to block 208).

The indication of the Delta-V associated with the crash of the vehicle102 may be an indication of Delta-V as used in vehicle crash analysis,and thus may be an indication of the difference between the velocity ofthe vehicle 102 before and after the crash of the vehicle 102. Highervalues of Delta-V may, for example, indicate higher vehicle crashseverities, higher likelihoods of injuries in vehicle crashes, etc.

Furthermore, in some embodiments, the actions described with respect toblock 212 may also or alternatively include generating one or more othersuitable indications, such as, for example, an indication of a number ofoccupants of the vehicle 102 at the time of the crash. The indication ofthe number of occupants of the vehicle 102 at the time of the crash maybe generated based on, for example, the one or more processors of thefirst mobile computing device 116 causing the first mobile computingdevice 116 to operate in a beacon receive mode to receive a signal orsignals from an additional mobile computing device(s) that may operatein a beacon transmit mode. The signal(s) received from the additionalmobile computing device(s) may include, for example, one or moreindication(s) from the additional mobile computing device(s) that acrash of the vehicle 102 has occurred. The additional mobile computingdevice(s) may transmit BLUETOOTH® signals, for example. The low power ofBLUETOOTH® signals may allow an assumption that any BLUETOOTH® signalreceived by the first mobile computing device 116 from an additionalmobile computing device is received from an additional mobile computingdevice that is located within the vehicle 102, and thus associated withan occupant of the vehicle 102. In this manner, the indication of thenumber of occupants of the vehicle 102 may be determined. It will beappreciated, however, that any suitable type(s) of signal(s) may betransmitted by the additional mobile computing device(s). Additionally,the indication of the number of occupants of the vehicle 102 may bedetermined in any suitable manner and need not utilize, for example, thebeacon transmit and beacon receive mode features described herein.

Additionally or alternatively, the signal(s) transmitted by theadditional mobile computing device(s) (e.g., BLUETOOTH® signals) mayinclude location information of the additional mobile computingdevice(s), such as Global Positioning System (GPS) information. Forexample, the aforementioned app for crash detection, as installed oneach of the additional mobile computing device(s), may cause each of theadditional mobile computing device(s) to transmit such locationinformation, which location information may be received using the one ormore processors of the first mobile computing device 116. Such locationinformation may be compared, such as using the one or more processors ofthe first mobile computing device 116, with location information of thefirst mobile computing device 116 to determine whether the additionalmobile computing device(s) are within the vehicle 102 and associatedwith additional occupant(s) of the vehicle 102.

With continued reference to the actions described with respect to block212, and with particular reference to the aforementioned beacon receiveand beacon transmit modes, in one embodiment, the aforementioned app forcrash detection may be installed on the first mobile computing device116 and each of the additional mobile computing device(s) (e.g., thesecond mobile computing device 122 and/or other mobile computingdevice(s) such as those discussed with respect to FIG. 5). The app maybe configured such that when the one or more processors of the firstmobile computing device 116 determine that the base sensor dataindicates that a condition corresponding to a crash of the vehicle 102has occurred, the first mobile computing device 116 is caused to operatein the beacon receive mode. The app for crash detection may also beconfigured such that when the first mobile computing device 116 iscaused to operate in the beacon receive mode, the additional mobilecomputing device(s) are caused to operate or remain operating in thebeacon transmit mode.

More particularly, in one embodiment, the app may be configured to causethe one or more processors of the first mobile computing device 116 tocause the first mobile computing device 116 to transmit a signal to theadditional mobile computing device(s) indicating that the base sensordata of the first mobile computing device 116 indicates that a conditioncorresponding to a crash has occurred. When the first mobile computingdevice 116 transmits such a signal to the additional mobile computingdevice(s), the app may be configured to cause the one or more processorsof the first mobile computing device 116 to cause the mobile computingdevice 116 to begin operating in the beacon receive mode. Additionally,when the first mobile computing device 116 transmits such a signal tothe additional mobile computing device(s), the app may be configuredsuch that upon receipt of such a signal by the additional mobilecomputing device(s), the app as installed on the additional mobilecomputing device(s) causes the additional mobile computing device(s) tooperate in the beacon transmit mode.

As will be apparent from the above description, and as should beappreciated with respect to all examples presented in this disclosure,various ones of the functions or operations shown in FIG. 3 areoptional. Furthermore, the functions or operations shown in FIG. 3 (andeach flow chart herein) may be performed in any suitable order, anydesired number of times, and/or with any suitable variation to theparticular order and/or combination shown so as to achieve a desiredresult, such as a desired manner of generating an indication of whethera crash of a vehicle (e.g., the vehicle 102) has occurred.

IV. Example Method For Providing Post-Crash Information after IndicationThat Vehicle Crash Has Occurred

FIG. 4 is a flow chart of an example method, routine, or process 300 forproviding post-crash information after an indication that a vehiclecrash has occurred. It will be appreciated from the teaching anddisclosure below that various features of the example method, routine,or process 300 may be further features of the example method, routine,or process 200.

One or more processors, which may be one or more processors of the firstmobile computing device 116, may determine whether the indication ofwhether the crash of the vehicle 102 has occurred (e.g., as describedwith respect to block 210) is an indication that the crash of thevehicle 102 has occurred (block 302). If it is determined that theindication of whether the crash of the vehicle 102 has occurred is anindication that the crash of the vehicle 102 has not occurred, themethod 300 may remain at the determination described with respect toblock 302 until it is determined that the indication of whether thecrash of the vehicle 102 has occurred is an indication that the crash ofthe vehicle 102 has occurred.

If it is determined that the indication of whether the crash of thevehicle 102 has occurred is an indication that the crash of the vehicle102 has occurred, the one or more processors may determine whether thevehicle 102 is stopped (block 304). For example, the one or moreprocessors may use location information (e.g., GPS information) of thefirst mobile computing device 116 to determine whether the location ofthe first mobile computing device 116 is changing, and thus that thevehicle 102 is not stopped, or whether the location of the first mobilecomputing device 116 is not changing and thus the vehicle 102 isstopped. The one or more processors may perform any suitable additionalor alternative actions to determine whether the vehicle 102 is stopped.If it is determined that the vehicle 102 is not stopped, the method 300may remain at the determination described with respect to block 304until it is determined that the vehicle 102 is stopped.

If it is determined that the vehicle 102 is stopped, the one or moreprocessors may cause at least one of a notification of the crash of thevehicle 102 or a prompt associated with the crash of the vehicle 102 tobe provided to the user (e.g., insured party such as the driver 112) ofthe first mobile computing device 116, such as via a user interface(e.g., display and/or other suitable user interface component(s)) of thefirst mobile computing device 116 (block 306). The notification and/orprompt may indicate that the first mobile computing device 116 hasgenerated an indication that the crash of the vehicle 102 has occurred,and in some embodiments may prompt the user to confirm that the crash ofthe vehicle 102 has actually occurred or, alternatively, to indicatethat the vehicle 102 has not been involved in a crash. For example, thebase sensor data and/or the additional sensor data may represent a“false alarm” and thus indicate a crash when a crash has not actuallyoccurred. Such a false alarm may occur if, for example, the first mobilecomputing device 116 is dropped while within the vehicle 102, orotherwise experiences a sudden movement and/or change in movement eventhough the vehicle 102 is not involved in a crash.

The one or more processors may determine whether the user has confirmed(e.g., via the user interface of the first mobile computing device 116)that the crash of the vehicle 102 occurred (block 308). If it isdetermined that the user has indicated that the crash of the vehicle 102has not occurred, the method may end (block 310). If it is determinedthat the crash of the vehicle 102 has occurred (e.g., that the user hasconfirmed that the crash of the vehicle 102 has occurred), it may bedetermined whether the user wishes to send data regarding the crash ofthe vehicle 102 from the first mobile computing device 116 to theinsurance provider (block 312). For example, the notification and/orprompt provided to the user may include an inquiry as to whether theuser wishes to send the data regarding the crash to the insuranceprovider. The inquiry may be presented, for example, by way of an optionon a touch screen display of the first mobile computing device 116. Inone embodiment, the inquiry as to whether the user wishes to send thedata regarding the crash to the insurance provider may be presented viathe touch screen display after the user selects a previous optionpresented via the touch screen display to confirm that the crash hasoccurred, as discussed with respect to block 308.

If it is determined with respect to block 312 that the user wishes tosend the data regarding the crash to the insurance provider, the one ormore processors may send the data regarding the crash of the vehicle 102to the insurance provider (block 314). For example, the one or moreprocessors may cause the data regarding the crash of the vehicle 102 tobe sent using at least a portion of an I/O circuit, such as the I/Ocircuit 170, to the remote computing device(s) 106 via the computernetwork 104. As further discussed below, the data regarding the crash ofthe vehicle 102 that is sent by the first mobile computing device 116 tothe insurance provider may be used by the insurance provider to, forexample, facilitate the initiation of a claim submission by the insuredparty without the insured party having to determine and provide suchdata to the insurance provider. In some embodiments, the data regardingthe crash of the vehicle 102 may be used as discussed herein and theinsured party may be asked, electronically or via phone, for example, toconfirm aspects of the data regarding the crash of the vehicle 102(e.g., that a crash occurred, a severity of the crash, a time of day,etc.) as received by the insurance provider. In some embodiments, thedata regarding the crash of the vehicle 102 may also or alternatively beused by the insurance provider as part of a general process ofdetermining correspondence between amounts of loss in claims andseverity of vehicle crashes. The results of such determinations may beused, for example, by the crash detection app to improve determinationsof indications of severity as described herein.

If it is determined with respect to block 312 that the user does notwish to send the data regarding the crash to the insurance provider, theone or more processors may cause one or more indications of one or moreother options for informing the insurance provider of the crash of thevehicle 102 and, for example, initiating a claim with the insuranceprovider with respect to the crash, to be provided to the user of thefirst mobile computing device 116 (block 316). For example, the one ormore processors may cause the first mobile computing device 116 todisplay, or otherwise provide via a user interface, one or more of acontact telephone number for the insurance provider; one or more contactaddresses for the insurance provider; a list of information that shouldbe provided to the insurance provider when initiating a claim with theinsurance provider with respect to the crash; an option(s) to schedule atime for a claim representative of the insurance provider to contact theuser, such as by providing one or more suitable touch screen options;and/or any other suitable information for initiating a claim with theinsurance provider.

With continued reference to the actions performed when it is determinedwith respect to block 312 that the user wishes to send the dataregarding the crash of the vehicle 102 from the first mobile computingdevice 116 to the insurance provider, as noted above with respect toblock 314, the one or more processors may send such data to theinsurance provider. With continued reference to the actions describedwith respect to block 314, in one embodiment, such data may beconsidered claim information and may be stored (e.g., in the database108) for use in processing a claim when, for example, the user calls theinsurance provider to proceed with claim processing, as furtherdiscussed below. In another embodiment, the data regarding the crash ofthe vehicle 102 may be stored (e.g., in the database 108) but may not beconsidered claim information. For example, the user may be asked todecide at a later time, such as when calling the insurance provider asdescribed below, if the user wishes to submit a claim with respect tothe crash of the vehicle 102, and if the user does wish to submit aclaim, the stored data regarding the crash may then be considered claiminformation and may be used in processing the claim.

The one or more processors may initiate a telephone call from the firstmobile computing device 116 to the insurance provider, such as via thecomputer network to the call management device(s) 110 (block 318). Theinitiating of the telephone call may include the one or more processorsmaking available to the insurance provider identifying data associatedwith the first mobile computing device 116, where the identifying dataassociated with the first mobile computing device 116 may correlate thefirst mobile computing device 116 with the data regarding the crash ofthe vehicle 102. For example, the identifying data may be a telephonenumber of the first mobile computing device 116 where the first mobilecomputing device 116 is a smart phone, and may thus be made availableautomatically when the telephone call is initiated from the first mobilecomputing device 116 to the insurance provider. In another example, theidentifying data may be an insurance policy number of the user of thefirst mobile computing device 116 (e.g., the insured party), and the oneor more processors of the first mobile computing device 116 may causethe insurance policy number to be transmitted to the call managementdevice(s) 110, for example, when the telephone call is initiated.Generally speaking, the identifying data associated with the firstmobile computing device 116 may be any suitable data that correlates thefirst mobile computing device 116 with the data regarding the crash ofthe vehicle 102, and allows the insurance provider to determine that thedata regarding the crash of the vehicle 102 corresponds to the firstmobile computing device 116.

In one embodiment, when the telephone call is initiated, the callmanagement device(s) 110 may perform a lookup of the identifying datamade available to the insurance provider by communicating with, forexample, one or more of the remote computing device(s) 106, such as aninsurance provider server. For example, when the identifying data madeavailable to the insurance provider is a telephone number of the firstmobile computing device 116, the call management device(s) 110 may querythe one or more of the remote computing device(s) 106, or otherwisecommunicate with the one or more of the remote computing device(s) 106,to match the telephone number with data regarding a vehicle crash. Insome cases, the data regarding the vehicle crash may have been stored inthe database 108, and the remote computing device(s) 106 may in turnquery or otherwise communicate with the database 108 in response to thequery or other communication from the call management device(s) 110. Inother examples, the call management device(s) 110 may query or otherwisecommunicate with the database 108 instead of querying or otherwisecommunicating with the remote computing device(s) 106. The callmanagement device(s) 110 may similarly communicate with the remotecomputing device(s) 106 or the database 108 when the identifying datamade available to the insurance provider (e.g., transmitted to the callmanagement device(s) 110) is data other than a telephone number, such asan insurance policy number as discussed above.

In any event, with continued reference to the actions described withrespect to block 318, the data regarding a vehicle crash thatcorresponds to (correlates with) the first mobile computing device 116(e.g., the data regarding the crash of the vehicle 102) may be retrievedfrom one or more of the remote computing device(s) 106 or from thedatabase 108 using the identifying data made available to the insuranceprovider. If the data regarding the crash of the vehicle 102 isconsidered claim information, as discussed above, one or more of thecall management device(s) 110, which may be located at a claimprocessing center of the insurance provider, may use such claiminformation to populate fields of a claim that may be shown on acomputing device display to an employee or contractor of the insuranceprovider. For example, the fields of the claim may be populated usingsuch claim information when an employee or contractor of the insuranceprovider answers the telephone call. Such claim information may include,for example, one or more of an indication of a time of the crash of thevehicle 102, an indication of a location (e.g., using GPS coordinates)of the crash of the vehicle 102, an indication of a severity of thecrash of the vehicle 102, and/or any other suitable claim information.

With further reference to the actions described with respect to block318, in examples where the data regarding the crash of the vehicle 102is not considered claim information, as discussed above, the user mayneed to decide whether to submit a claim with regard to the crash of thevehicle 102 when the telephone call from the first mobile computingdevice 116 to the insurance provider is initiated. For example, the usermay inform an employee or contractor of the insurance provider whoanswers the telephone call, or may inform an automated service thatanswers the telephone call, that the user wishes to submit a claim. Thedata regarding the crash of the vehicle 102 may then, for example, bepopulated into fields of a claim that may be shown on a computingdevice, or may otherwise be used to facilitate the claim process.

In some embodiments, the user (e.g., insured party such as the driver112) may be requested to provide additional information to establish orcomplete a First Notice of Loss (FNOL). As such, the one or moreprocessors may receive and/or provide one or more of apost-crash-detection indication(s) from and/or to the user (e.g.,insured party) of the first mobile computing device 116; apost-crash-detection request(s) from and/or to the user; apost-crash-detection input(s) from the user; or any other suitableinformation from and/or to the user (block 320).

More particularly, in various embodiments, the one or more processors ofthe first mobile computing device 116 may at least one of receive anindication from the user of the first mobile computing device 116 of aseverity of the crash of the vehicle 102; receive (e.g., from memory ofthe first mobile computing device 116) and provide to the user anindication of at least one of at least one individual or at least oneentity for the user to contact regarding the crash of the vehicle (e.g.,an emergency contact person, the insurance provider, etc.); receive anindication from the user (e.g., by way of a text message, such as inresponse to a prompt sent to the first mobile computing device 116 afterthe user confirms that the crash of the vehicle 102 has occurred) ofwhether any occupant of the vehicle has been injured in the crash of thevehicle 102; receive a request from the user for information regardingpost-crash guidelines (e.g., suggestions regarding how to communicatewith a driver of another vehicle involved in the crash, a reminder toget insurance information of the driver of the other vehicle involved inthe crash, etc.) for the user to follow after the crash of the vehicle102 and/or provide such information regarding post-crash guidelines tothe user; receive an input from the user to adjust data regarding thecrash of the vehicle 102 that is to be sent to the insurance provider(e.g., default text or other element(s) of an electronic communicationto be sent to the insurance provider to provide data regarding thecrash, such as the data regarding the crash as described with respect toblocks 312 and 314); receive a request from the user to view via a userinterface of the first mobile computing device 116 one or more images ofan insurance card corresponding to the insurance coverage associatedwith the vehicle 102; provide such one or more images of the insurancecard via the user interface for viewing by the user; receive a requestfrom the user for a tow truck to be deployed to a location of the crashof the vehicle 102; receive a request from the user for transportationof the user (e.g., as facilitated by the insurance provider) from thelocation of the crash of the vehicle 102; receive a request from theuser for the insurance provider to arrange use of a rental vehicle forthe user; receive an input from the user to initiate an electronic claimprocess to file a claim associated with the crash of the vehicle 102with the insurance provider; receive an input from the user to initiatecontact via the first mobile computing device 116 (e.g., by way of atelephone call) with an agent of the insurance provider; and/or receiveand/or provide any other suitable and/or desired indication(s),request(s), input(s), or other information.

V. Example System For Generating Vehicle Crash Data

FIG. 5 illustrates the example system 100 for generating vehicle crashdata in greater detail. As shown in FIG. 5, the system 100 may includethe vehicle 102, the computer network 104, the remote computingdevice(s) 106, the database 108, and the call management device(s) 110.The vehicle 102 is shown as including the driver seat 114, the frontpassenger seat 120, a left rear passenger seat 402, and a right rearpassenger seat 404. In the example of FIG. 5, the first mobile computingdevice 116 may be associated with (e.g., possessed by) a driver (notshown in FIG. 5) sitting in the driver seat 114, and the second mobilecomputing device 122 may be associated with a passenger (not shown inFIG. 5) sitting in the front passenger seat 120. FIG. 5 also illustratesa third mobile computing device 406 and a fourth mobile computing device408, which may be a smart watch. The third and fourth mobile computingdevices 406 and 408 may be associated with occupants (not shown in FIG.5) of the left rear passenger seat 402 and the right rear passenger seat404, respectively.

As further illustrated in FIG. 5, the first, second, and third mobilecomputing devices 116, 122, and 406 may be communicatively coupled tothe computer network 104 so as to communicate with, for example, theremote computing device(s) 106 and the call management device(s) 110 ina similar manner as discussed above with respect to, for example, thefirst mobile computing device 116. In one embodiment, the smart watch408 may not directly communicate with the computer network 104 (e.g.,the Internet) but may communicate with the computer network 104indirectly by being communicatively coupled to another one of thecomputing devices, such as, for example, the first mobile computingdevice 116. With further reference to the discussion above, it will beappreciated that the configuration of computing devices and seats asshown in FIG. 5 is by way of example only. For example, the first,second, third, and fourth mobile computing devices 116, 122, 406, and408 may be in different seats than shown in FIG. 5; the vehicle 102 mayinclude more or fewer seats; the vehicle 102 may include more or fewercomputing devices; and/or any other suitable modifications to thearrangement shown in FIG. 5 may be made.

FIG. 5 also illustrates communication links from each one of the mobilecomputing devices 116, 122, 406, and 408 to each other one of the mobilecomputing devices 116, 122, 406, and 408. Each such communication linkmay be any suitable wireless or wired communication link. It will beappreciated that not all of the communication links between the mobilecomputing devices 116, 122, 406, and 408 shown in FIG. 5 need be presentin a particular embodiment. For example, a suitable subset of thecommunication links shown between the mobile computing devices 116, 122,406, and 408 shown in FIG. 5 may be present in a particular embodiment.In some embodiments, the communication links between the mobilecomputing devices 116, 122, 406, and 408 may be or may includeBLUETOOTH® communication links used in implementing a wireless ad hocnetwork in which each of the mobile computing devices 116, 122, 406, and408 operates in a beacon receive mode or a beacon transmit mode, asdiscussed above and further discussed below.

In some embodiments, the remote computing device(s) 106 may include oneor more insurance provider servers, as discussed above, and the one ormore insurance provider servers may be or may include one or more cloudcomputing servers with which the mobile computing devices 116, 122, 406,and 408 may communicate via the computer network 104.

VI. Example Methods For Generating Vehicle Crash Data

FIG. 6 is a flow chart of an example method, routine, or process 500 forgenerating vehicle crash data, such as data regarding a crash of thevehicle 102. One or more processors may determine whether the firstmobile computing device 116 within the vehicle 102 has detected that acrash of the vehicle 102 has occurred (block 502). In some embodiments,the one or more processors may be or may include one or more processorsof the first mobile computing device 116. The determination of whetherthe first mobile computing device 116 has detected that a crash of thevehicle 102 has occurred may be made, for example, in the mannerdescribed above with respect to, for example, FIG. 3. In someembodiments, the one or more processors may also or alternatively be orinclude one or more processors of one or more of the remote computingdevice(s) 106. In such embodiments, the determination of whether thefirst mobile computing device 116 has detected that a crash of thevehicle 102 has occurred may include receiving, using the one or moreprocessors of the one or more of the remote computing device(s) 106, anindication from the first mobile computing device 116 of whether thecrash of the vehicle 102 has occurred. Such an indication may bedetermined, for example, in the manner described above with respect toFIG. 3.

If it is determined with respect to block 502 that the first mobilecomputing device 116 has not detected that a crash of the vehicle 102has occurred, the one or more processors may determine whether at leasta second mobile computing device (e.g., the second mobile computingdevice 122 and/or the third mobile computing device 406) within thevehicle 102 has detected that a crash of the vehicle 102 has occurred(block 504). For example, one or more processors of the first mobilecomputing device 116 may determine whether the first mobile computingdevice 116 has received an indication from the at least the secondmobile computing device (e.g., one or more of the mobile computingdevices 122 or 406) that the crash of the vehicle 102 has occurred. Suchan indication may be determined by the at least the second mobilecomputing device in the manner described above with respect to FIG. 3,for example. In some embodiments, the one or more processors may also oralternatively be or include one or more processors of one or more of theremote computing device(s) 106, as discussed with respect to block 502.In such embodiments, the determination of whether the at least thesecond mobile computing device has detected that a crash of the vehicle102 has occurred may include receiving, using the one or more processorsof the one or more of the remote computing device(s) 106, an indicationfrom the at least the second mobile computing device of whether thecrash of the vehicle 102 has occurred. As discussed above, such anindication may be determined, for example, in the manner described withrespect to FIG. 3.

If it is determined with respect to block 504 that the at least thesecond mobile computing device has not detected that a crash of thevehicle 102 has occurred, the method 500 may return to the determinationas described with respect to the block 502, and thus the method 500 maynot proceed past the determinations described with respect to blocks 502and 504 until it is determined that at least one of the first or the atleast the second mobile computing devices has detected that a crash hasoccurred. Conversely, if it is determined with respect to either block502 or block 504 that the first mobile computing device 116 (block 502)or the at least the second mobile computing device (block 504) hasdetected that a crash of the vehicle 102 has occurred, the one or moreprocessors may receive sensor data output by at least one sensor (block506). More particularly, with continued reference to the actionsdescribed with respect to block 506, the at least one sensor may be atleast one sensor of at least one of the first mobile computing device116 or the at least the second mobile computing device. The sensor dataoutput by the at least one sensor of the at least one of the firstmobile computing device 116 or the at least the second mobile computingdevice may be associated with the detected crash of the vehicle 102(e.g., by being sensor data output at a time that matches a time of thedetected crash of the vehicle 102).

The one or more processors may receive further sensor data output by atleast one sensor of a further mobile computing device (e.g., the fourthmobile computing device 408, which as noted above may be a smart watch,for example) (block 508). The at least one further sensor may include atleast one sensor of the types of sensors 152-160 discussed with respectto the computing device 150, for example. The further mobile computingdevice may be communicatively coupled to the first mobile computingdevice 116 (e.g., by way of the fourth mobile computing device 408 beingcommunicatively coupled, such as via BLUETOOTH® communication, to thefirst mobile computing device 116), and the further sensor data may beassociated with the detected crash of the vehicle 102 (e.g., by beingsensor data output at a time that matches a time of the detected crashof the vehicle 102). In some embodiments, the further sensor data may beused in generating vehicle crash data as described below. As discussedabove with reference to the actions described with respect to blocks 502and 504, the one or more processors may be or may include one or moreprocessors of, for example, the first mobile computing device 116 and/orone or more of the remote computing device(s) 106, and the furthersensor data may be received accordingly. For example, in an embodimentwhere the one or more processors include one or more processors of oneor more of the remote computing device(s) 106 (such as one or moreprocessors of a cloud computing device of the insurance provider), andwhere the further mobile computing device is communicatively coupled tothe first mobile computing device 116, the one or more processors mayreceive the further sensor data from the first mobile computing device116.

The one or more processors (which, again, may be or may include one ormore processors of, for example, the first mobile computing device 116and/or one or more of the remote computing device(s) 106) may generatethe vehicle crash data (block 510). More particularly, with continuedreference to the actions described with respect to block 510, the one ormore processors may generate the vehicle crash data based on the sensordata associated with the detected crash of the vehicle 102 as output bythe at least one sensor of the at least one of the first mobilecomputing device 116 or the at least the second mobile computing device.For example, by analyzing such sensor data, the one or more processorsmay generate the vehicle crash data so that the vehicle crash dataincludes at least one of an initial confirmation that the crash of thevehicle 102 has occurred, an indication of a severity of the crash ofthe vehicle 102, an indication of a number of occupants of the vehicle102 at a time of the crash, or an indication that the crash of thevehicle 102 has not occurred.

With continued reference to the actions described with respect to block510, in one embodiment, the first mobile computing device 116 or one ormore of the at least the second mobile computing device may havedetected that the crash of the vehicle 102 has occurred, and sensor datareceived from another mobile computing device(s) of the first and/orsecond mobile computing device(s) as described with respect to block 508may provide a confirmation that the crash has occurred or, conversely,may provide an indication that the crash has not actually occurred. Inone embodiment, where any of the first mobile computing device 116 orthe at least the second mobile computing device detects that the crashof the vehicle 102 has occurred, as described with respect to blocks 502and 504, a subsequent indication that the crash has not actuallyoccurred as described with respect to block 510 may be used by themobile computing device(s) that detected the crash in, for example, amachine learning process as described above. Such use in a machinelearning process, for example, may improve the accuracy of crashdetection, severity classification, etc. by the mobile computingdevice(s) that detected the crash.

With further reference to the actions described with respect to block510, in some embodiments, the one or more processors may additionally oralternatively generate the vehicle crash data based on, for each one ofthe first mobile computing device 116 and/or the at least the secondmobile computing device, at least one of (i) a respective geographiclocation of the mobile computing device (e.g., as determined by a GPSunit of the mobile computing device), or (ii) a respective indication ofa time (e.g., as determined by the mobile computing device) that atleast a portion of the sensor data output by the at least one sensor ofthe at least one of the first mobile computing device 116 or the atleast the second mobile computing device was output by at least onesensor of the respective mobile computing device. In this manner, thevehicle crash data may be generated based on collating sensor data fromdifferent ones of the mobile computing devices based on indicatedgeographic locations and/or times at which the sensor data of thedifferent mobile computing devices was output.

Among other advantages, generation of the vehicle crash data in thismanner may be more likely to accurately account for differences insensor outputs among the mobile computing devices (e.g., the mobilecomputing devices 116, 122, and 406) based on a subset of the mobilecomputing devices being relatively farther apart from one another ascompared to another subset of the mobile computing devices. Additionallyor alternatively, among other advantages, if, for example, one of themobile computing devices 116, 122, or 406 outputs sensor data at anindicated time that is different from indicated times at which theothers of the mobile computing devices 116, 122, or 406 output sensordata, the sensor data output by the one of the mobile computing devicesmay be treated with relatively lower importance or weight in theanalysis of the sensor data and generation of the vehicle crash data.

More generally, use of sensor data from multiple mobile computingdevices as described herein may improve the accuracy of the vehiclecrash data even without use of indicated geographic locations and/ortimes at which the sensor data of different ones of the multiple mobilecomputing devices was output. For example, a mobile computing device,such as a smart phone, may experience significant movement unrelated toany vehicle crash, such as if the mobile computing device is dropped,moved suddenly by a user from one hand to another, picked up or put downby the user, re-oriented by the user, etc. By using sensor data frommultiple mobile computing devices in the vehicle 102, sensor data thatmay correspond to sensor data present when a crash occurs but that doesnot actually reflect a crash may have less influence on the generatedvehicle crash data, because sensor data from another mobile computingdevice(s) in the vehicle 102 is relatively unlikely to correspond tosensor data present when a crash occurs unless a crash has actuallyoccurred. Additionally, the use of multiple mobile computing devices asdescribed herein may improve aspects of the vehicle crash data such asthe indicated severity, indicated number of occupants, etc. by providingmore sensor data upon which to base such indications. Still further, theuse of multiple mobile computing devices as described herein may improveaccuracy of the vehicle crash data by providing sensor data from one ormore mobile computing devices that may have more sensitive sensors(e.g., the first mobile computing device 116) to augment sensor datafrom one or more mobile computing devices that may, for example, be lessexpensive and/or incorporate older technology and thus have lesssensitive sensors, for example (e.g., the second mobile computing device122).

With still further reference to the actions described with respect toblock 510, in some embodiments, the one or more processors mayadditionally or alternatively generate the vehicle crash data based onthe further sensor data. As such, sensor data from, for example, thefourth mobile computing device 408 (e.g., a smart watch) may also beutilized in generating the vehicle crash data, even in examples such asthat shown in FIG. 5 where the further (e.g., fourth) mobile computingdevice communicates with the computer network 104 indirectly through oneof the first, second, or third mobile computing devices 116, 122, or406.

FIG. 7 is a flow chart of another example method, routine, or process600 for generating vehicle crash data, such as data regarding a crash ofthe vehicle 102. It will be appreciated from the teaching and disclosureherein that actions described with respect to the example method,routine, or process 600 of FIG. 7 may constitute particularimplementations of actions described with respect to the example method,routine, or process 500 of FIG. 6.

One or more processors may determine whether the first mobile computingdevice 116 within the vehicle 102 has detected that a crash of thevehicle 102 has occurred based on at least a portion of the sensor dataoutput by the at least one sensor of the at least one of the firstmobile computing device 116 or the at least the second mobile computingdevice, where the at least the portion of such sensor data includessensor data output by at least one sensor of the first mobile computingdevice 116 (block 602). It will be appreciated that the actionsdescribed with respect to block 602 may correspond to a more particularimplementation of the actions described with respect to block 502 ofFIG. 6. Additionally, in various embodiments, the one or more processorsmay be or may include one or more processors of the first mobilecomputing device 116 and/or one or more processors of one or more of theremote computing device(s) 106, for example.

The one or more processors may cause the first mobile computing device116 to operate in a beacon receive mode to receive a signal indicatingthat the crash of the vehicle 102 has occurred (block 604). Withreference to the discussion above, in some embodiments, the first mobilecomputing device 116 may be caused to operate in the beacon receive modeafter it is determined that the first mobile computing device 116 hasdetected that the crash of the vehicle 102 has occurred. For example,with reference to the discussion of FIG. 3 above, the first mobilecomputing device 116 may in some embodiments transmit a signalindicating that base sensor data received by one or more processors ofthe first mobile computing device 116 indicates that a conditioncorresponding to a crash has occurred, and the signal may be receivedby, for example, the second, third, and fourth mobile computing devices122, 406, and 408. In other embodiments, the first mobile computingdevice 116 may transmit such a signal when the first mobile computingdevice 116 has detected a crash of the vehicle 102 (e.g., when the oneor more processors generate an indication that the crash has occurredbased on, for example, additional sensor data associated with the firstmobile computing device 116 as described above). In such embodiments,the signal may be received by, for example, the second, third, andfourth mobile computing devices 122, 406, and 408. In some embodiments,when the first mobile computing device 116 transmits such a signal, theone or more processors may cause the first mobile computing device 116to begin operating in the beacon receive mode, as further discussedabove with respect to FIG. 3. With further reference to the discussionof FIG. 3, upon receipt of such a signal, the second, third, and fourthmobile computing devices 122, 406, and 408 may be caused to operate in abeacon transmit mode.

With continued reference to the actions described with respect to block604, the mobile computing devices 116, 122, 406, and 408 may thus form awireless ad hoc network using, for example, BLUETOOTH® communicationwith the first mobile computing device 116 operating in a beacon receivemode after detecting a crash or a crash condition, and with theremaining mobile computing devices operating in a beacon transmit mode.It will be appreciated, however, that any suitable ad hoc network may beformed, which may or may not utilize BLUETOOTH® communication, and/orwhich may or may not include the mobile computing devices 116, 122, 406,and 408 operating in beacon receive and beacon transmit modes such asdescribed above. It will further be appreciated that while the firstmobile computing device 116 is at times described herein as detectingthe crash of the vehicle 102 or the crash condition, in variousembodiments, each of the mobile computing devices 116, 122, 406, and 408may detect the crash of the vehicle 102 at any time. In suchembodiments, for example, the one of the mobile computing devices 116,122, 406, or 408 that detects the crash of the vehicle 102 first mayperform the actions described herein as being performed by the firstmobile computing device 116 (e.g., operating in a beacon receive mode orotherwise “listening for” or receiving one or more signals from theother mobile computing devices indicative of detection of the crash ofthe vehicle 102).

The one or more processors may determine whether the first mobilecomputing device 116 operating in the beacon receive mode has receivedthe signal indicating that the crash of the vehicle 102 has occurredfrom at least one of the at least the second mobile computing device(e.g., at least one of the second mobile computing device 122 or thethird mobile computing device 406) (block 606). In this manner, themobile computing device (e.g., the first mobile computing device 116)that first detects that the crash of the vehicle 102 has occurred maydetermine whether other nearby devices have also detected that the crashof the vehicle 102 has occurred. As described with respect to block 604,in other embodiments, the first mobile computing device 116 maycommunicate with the mobile computing devices 122, 406, and/or 408, forexample, in any suitable wireless ad hoc network, which need not utilizebeacon transmit and beacon receive modes and/or which need not utilizeBLUETOOTH® communication.

With continued reference to the actions described with respect to block606, and as discussed above with respect to FIG. 6, the combination ofdata from multiple mobile computing devices regarding whether the crashof the vehicle 102 has been detected may improve the accuracy of thevehicle crash data generated by, for example, the first mobile computingdevice 116. Thus, for example, the first mobile computing device 116 maydetect a crash, but no other mobile computing device may detect a crash,and the vehicle crash data generated by the first mobile computingdevice 116 may indicate that no crash actually occurred (with suchvehicle crash data depending, for example, upon factors such asgeographic location and/or times of sensor outputs). In this example,the first mobile computing device 116 may be caused (e.g., by theaforementioned app executed by the one or more processors) to change,for example, the manner in which the first mobile computing device 116analyzes sensor data to detect whether the crash of the vehicle 102 hasoccurred, and thus may provide more accurate detection data for use inultimately generating the vehicle crash data as described herein. Withreference to the discussion of FIG. 6, such changing of the manner inwhich the first mobile computing device 116 analyzes, for example,sensor data may result from, for example, a machine learning processimplemented using the first mobile computing device 116.

With further reference to the actions described with respect to block606, it will also be appreciated that grouping or collating of data frommobile computing devices based on geographic location and/or times ofsensor outputs, such as in the manner discussed above with respect toFIG. 6, may accurately account for differences in sensor outputs amongthe mobile computing devices. Furthermore, when two mobile computingdevices have an existing relationship other than a wireless ad hocnetwork, such as the fourth mobile computing device 408 (e.g., a smartwatch) being communicatively coupled to the first mobile computingdevice 116, sensor data output by each of such two mobile computingdevices (e.g., the fourth mobile computing device 408 and the firstmobile computing device 116) may be compared. In this manner, forexample, the accuracy of generating the vehicle crash data may befurther increased by assessing related sensor data from multipleperspectives.

It will be appreciated in light of the teaching and disclosure hereinthat actions described with respect to blocks 604 and 606 may correspondto implementations of the actions described with respect to block 504.

The one or more processors may also send the sensor data output by theat least one sensor of the at least the first mobile computing device116 or the at least the second mobile computing device to one or more ofthe remote computing device(s) 106 (block 608). For example, one or moreprocessors of the first mobile computing device 116 may send such sensordata to a cloud computing device (e.g., cloud computing server) of theinsurance provider, which cloud computing device may be one of theremote computing device(s) 106. As noted above, the one or moreprocessors may include one or more processors of one or more of theremote computing device(s) 106, and as such may include one or moreprocessors of such a cloud computing device. Consequently, in someembodiments, the aforementioned sensor data may be analyzed by one ormore processors of such a cloud computing device, and the one or moreprocessors of such a cloud computing device may perform the generationof the vehicle crash data as described with respect to, for example,block 510 of FIG. 6.

VII. Example Computing Device For Generating Data Regarding a VehicleCrash

FIG. 8 illustrates an implementation of the example computing device 150and components thereof that may be used in generating data regarding avehicle crash, such as a crash of the vehicle 102 as described herein.As described with respect to FIG. 2, an instance or instances of thecomputing device 150, or portions thereof, may be an implementation(s)of any suitable computing device such as, for example, one or more ofthe first, second, third, or fourth mobile computing devices 116, 122,406, or 408. As shown in FIG. 8, the computing device 150 may includeone or more sensors 702, which may be or may include, for example, anysuitable one or more of the sensors 152-160 described above with respectto FIG. 2. The remaining description of the computing device 150 withrespect to FIG. 8 will include description of components not also shownin FIG. 2, it being understood that the components shown in FIG. 8 andalso shown in FIG. 2 may be configured and/or may operate in the mannerdescribed with respect to FIG. 2.

As shown in FIG. 8, the computing device 150 may include a buffer 704,where the buffer may be a suitable portion of the memory 168 thatincludes, for example, data 706-716. In one embodiment, before a crashof the vehicle 102 is detected, the data 706-716 may include, forexample, initial sensor data output by at least one sensor of a mobilecomputing device (e.g., the first mobile computing device 116) of whichthe computing device 150 is an implementation. In particular, first data706 may be a first received element of the initial sensor data output bythe sensor(s) of the first mobile computing device 116 and, as shown inFIG. 8, is designated “DATA0.” Second data 708 may be a second receivedelement of the initial sensor data output by the sensor(s) and may bedesignated “DATA1.” Third data 710 may be a third received element ofthe initial sensor data output by the sensor(s) and may be designated“DATA2.” Fourth data 712 may be a fourth received element of the initialsensor data output by the sensor(s) and may be designated “DATA3.” Fifthdata 714 may be a fifth received element of the initial sensor dataoutput by the sensor(s) and may be designated “DATA4.” Sixth data 716may be a sixth received element of the initial sensor data output by thesensor(s) and may be designated “DATA5.”

In some embodiments, the buffer 704 may be a first-in first-out (FIFO)buffer. Additionally or alternatively, in some embodiments, the buffer704 may be implemented as a circular buffer. As such, if a next (e.g.,seventh) element of initial sensor data (e.g., sensor data output by thesensor(s) of the first mobile computing device 116 that includes thebuffer 704) is received at the buffer 704, such a seventh element ofinitial sensor data, which may be designated “DATA6” may be written intothe buffer 704 as the first data 706, and may overwrite the firstreceived element of the initial sensor data designated as “DATA0.” Thatis, the first received element “DATA0,” which in this example is theoldest (e.g., earliest received) element of data, may be removed fromthe buffer 704 to make room for the seventh received element “DATA6.”Similarly, if an eighth element of initial sensor data, which may bedesignated “DATA7,” is received at the buffer 704, the eighth elementmay be written into the buffer 704 as the second data 708, and mayoverwrite the second received element “DATA1,” which would at the timeof receipt of the eighth element be the oldest element of data remainingin the buffer 704.

It will be appreciated in light of the teaching and disclosure hereinthat the buffer 704 may be of any suitable size (e.g., may includestorage space for any suitable number of data elements, such as morethan or less than six elements). As further described below with respectto FIG. 9, the contents of the buffer 704 may be stored in additionaldata storage 718 (e.g., as first sensor data 720 within the additionaldata storage 718) within the memory 168 when a crash of the vehicle 102is detected, and the buffer 704 may then receive post-crash sensor data.The post-crash sensor data, as further described below, may also bestored in the additional data storage 718 (e.g., as second sensor data722 within the additional data storage 718) to generate, for example, afile containing sensor data from both before and after the detectedcrash of the vehicle 102.

VIII. Example Method For Generating Data Regarding a Vehicle Crash

FIG. 9 is a flow chart of an example method, routine, or process 800 forgenerating data regarding a vehicle crash, such as a crash of thevehicle 102 as described herein. One or more processors, which may beone or more processors of the first mobile computing device 116, such asa microprocessor(s) implemented as shown and described with respect toFIGS. 2 and 8, may receive initial sensor data output by at least onesensor of a mobile computing device (e.g., the first mobile computingdevice 116), such as initial sensor data output by at least one sensorof the types of sensors 152-160 (block 802).

The one or more processors may store the initial sensor data in thebuffer 704, where as discussed above, the buffer 704 may be included inthe first mobile computing device 116 (block 804). In one embodiment,the buffer 704 may include storage capacity for a first amount of sensordata (e.g., six elements of sensor data as shown in the example of FIG.8). In another embodiment, the buffer 704 may include storage capacityfor the lower of a second amount of sensor data (which may be anysuitable amount of sensor data, and may be the same as or different fromthe first amount of sensor data) or an amount of sensor data thatcorresponds to a particular amount of time (e.g., a predetermined amountof time of collection of sensor output(s)).

In any event, the initial sensor data stored in the buffer 704 asdescribed with respect to block 804 may in some embodiments be regardedas including first and second portions. The one or more processors mayremove a portion of the initial sensor data (e.g., the second portion)from the buffer 704 when an amount of the initial sensor data exceeds astorage capacity of the buffer 704 (e.g., exceeds six elements of sensordata) (block 806). Thus, the second portion of the initial sensor datamay be the oldest initial sensor data in the buffer 704, which may beremoved from the buffer 704 (e.g., discarded, overwritten, etc.) whennewer initial sensor data is stored in the buffer 704 and the buffer 704no longer has storage capacity for the oldest initial sensor data.Correspondingly, the first portion of the initial sensor data may beregarded as the newest initial sensor data (e.g., that portion of theinitial sensor data that is not the oldest initial sensor data that isremoved from the buffer 704 as described above).

The one or more processors may determine whether the initial sensor dataoutput by the at least one sensor of the mobile computing device (e.g.,the first mobile computing device 116) and stored in the buffer 704includes sensor data indicating that a crash of the vehicle 102 hasoccurred (block 808). In some embodiments, each element of sensor datastored in the buffer 704 may include data from multiple sensors of thefirst mobile computing device 116, such as each of the sensors 152-160when each of the sensors 152-160 is outputting sensor data (as discussedwith respect to, for example, FIGS. 1 and 3). The determination ofwhether the initial sensor data output by the at least one sensor of themobile computing devices indicates that a crash of the vehicle 102 hasoccurred may be made in any suitable manner, such as by any suitableanalysis of the initial sensor data in the buffer 704, which may includereal-time analysis of the initial sensor data as the initial sensor datais received at and stored in the buffer 704. For example, thedetermination of whether the initial sensor data indicates that a crashof the vehicle 102 has occurred may be made in a similar manner asdiscussed above with respect to, for example, FIG. 3.

If it is determined with respect to block 808 that the initial sensordata does not indicate that a crash of the vehicle 102 has occurred, themethod 800 may return to the actions described with respect to block 802to continue receiving initial sensor data and performing the actionsdescribed with respect to blocks 804, 806, and/or 808 until it isdetermined that the initial sensor data indicates that a crash of thevehicle 102 has occurred. When it is determined with respect to block808 that the initial sensor data indicates that a crash of the vehicle102 has occurred, the one or more processors may receive an “indexidentifier” (“index ID”) indicating a particular sensor that provided asensor output(s) leading to the determination described with respect toblock 808 that the initial sensor data indicates that a crash hasoccurred (block 810). In another embodiment, multiple “index IDs”indicating multiple sensors may be received when multiple sensors of,for example, the first mobile computing device 116 provided sensoroutputs leading to the determination described with respect to block 808that the initial sensor data indicates that a crash has occurred.

The one or more processors may cause at least a portion of the initialsensor data stored in the buffer 704 to be stored in the additional datastorage 718 of the first mobile computing device 116 (block 812). Forexample, the at least the portion of the initial sensor data may be thefirst portion of the initial sensor data described above, and thus maybe the newest initial sensor data, with the oldest initial sensor data(e.g., the second portion of the initial sensor data) having notindicated that a crash has occurred and having been removed/discardedfrom the buffer 704 as described above. More particularly as to theactions described with respect to block 812, the one or more processorsmay cause the at least the portion of the initial sensor data stored inthe buffer 704 to be removed from the buffer 704 and stored as the firstsensor data 720 within the additional data storage 718, where the firstsensor data 720 thus is or includes sensor data corresponding to aperiod of time before the crash of the vehicle 102.

The one or more processors may receive additional sensor data output bythe at least one sensor of the mobile computing device (e.g., the firstmobile computing device 116) for an amount of time after it isdetermined that the initial sensor data output by the at least onesensor of the mobile computing device includes sensor data indicatingthat the crash of the vehicle 102 has occurred (block 814). The amountof time may be a predetermined amount of time corresponding to anexpected duration of the crash of the vehicle 102, in some examples. Forexample, an expected duration of a vehicle crash in general may bethree-tenths of a second, and thus the amount of time during which theadditional sensor data is received may be, in various embodiments,three-tenths of a second, a suitable amount of time longer thanthree-tenths of a second to provide a margin of error, etc. In oneembodiment, the additional sensor data may be received for the amount oftime by the one or more processors computing or otherwise determining anend time at which the one or more processors may stop receiving theadditional sensor data, where the end time may be based on a currenttime plus the amount of time during which the additional sensor data isto be received. The one or more processors may then receive theadditional sensor data until the computed or otherwise determined endtime.

The one or more processors may store the additional sensor data outputby the at least one sensor of the first mobile computing device 116 inthe buffer 704 (block 816). In view of the discussion above of the atleast the portion of the initial sensor data (e.g., the first portion ofthe initial sensor data) being removed from the buffer 704 and stored asthe first sensor data 720 within the additional data storage 718, thebuffer 704 may be empty at the time the additional sensor data begins tobe stored in the buffer 704. As also noted above, the buffer 704 mayhave one of several possible example storage capacities to store theadditional sensor data.

The one or more processors may generate combined sensor data based onthe initial sensor data stored as the first sensor data 720 and based onthe additional sensor data (block 818). Generating the combined sensordata may include causing, such as at the aforementioned end time, theadditional sensor data to be stored in the additional data storage 718as the second sensor data 722, where the second sensor data 722 may thuscorrespond to a period of time after the crash of the vehicle 102. Assuch, in some embodiments, the combined sensor data may include thefirst sensor data 720 and the second sensor data 722.

The one or more processors may correlate the combined sensor data withidentifying information associated with the mobile computing device(e.g., a telephone number of the first mobile computing device 116, aninsurance policy number of a user (e.g., insured party) of the firstmobile computing device 116, or any suitable identifying information)(block 820). The one or more processors may also make available thecorrelated combined sensor data and identifying data associated with themobile computing device to the insurance provider (block 822). Forexample, such data may be sent to the insurance provider (e.g., to oneor more of the remote computing device(s) 106) in the same or a similarmanner as described above with respect to sending data regarding thedetected crash to the insurance provider (e.g., as described withrespect to FIG. 4). Thus, as also described above, information may bepopulated into a claim or otherwise be more readily accessible to theinsurance provider if the user of the first mobile computing device 116,for example, initiates a claim regarding the crash electronically, by atelephone call to the insurance provider, etc.

It will be appreciated in light of the teaching and disclosure hereinthat the combined sensor data may have other suitable uses as well. Asjust one example, the second sensor data 722 may be compared with thefirst sensor data 720 and information such as differences between thefirst and second sensor data 720 and 722 (and if desired, one or moresensor-specific differences) may be used in a machine learning processsuch as that described above, may be used to improve severityclassification and thus to improve indications of severity that aredetermined as described herein, and/or may be used in any other suitablemanner.

IX. Additional Considerations

The following additional considerations apply to the foregoingdiscussion. Throughout this specification, plural instances mayimplement functions, components, operations, or structures described asa single instance. As noted above, although individual functions andinstructions of one or more methods are illustrated and described asseparate operations, one or more of the individual operations may beperformed concurrently, and nothing requires that the operations beperformed in the order illustrated. Structures and functionalitypresented as separate components in example configurations may beimplemented as a combined structure or component. Similarly, structuresand functionality presented as a single component may be implemented asseparate components. These and other variations, modifications,additions, and improvements fall within the scope of the subject matterherein.

The methods described in this application may include one or morefunctions or routines in the form of non-transitory computer-executableinstructions that are stored in a tangible computer-readable storagemedium and executed using a processor of a computing device (e.g., thefirst mobile computing device 116, one or more of the remote computingdevice(s) 106, and/or any other computing devices within the examplesystem 100 in any suitable combination). The routines may be included aspart of any of the modules described in relation to FIG. 1 or as part ofa module that is external to the system illustrated by FIG. 1. Forexample, the methods or portions thereof may be part of a browserapplication(s) or an application(s) running on any of the devices in theexample system 100 as a plug-in or other module of the browserapplication. Further, the methods may be employed as“software-as-a-service” to provide, for example, the first mobilecomputing device 116, one or more of the remote computing device(s) 106,and/or any other computing devices with access to the example system100.

Additionally, certain aspects are described herein as including logic ora number of functions, components, modules, blocks, or mechanisms.Functions may constitute either software modules (e.g., non-transitorycode stored on a tangible machine-readable storage medium) or hardwaremodules. A hardware module is a tangible unit capable of performingcertain operations and may be configured or arranged in a certainmanner. In example embodiments, one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwaremodules of a computer system (e.g., a processor or a group ofprocessors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC) toperform certain functions). A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term hardware should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwaremodules are temporarily configured (e.g., programmed), each of thehardware modules need not be configured or instantiated at any oneinstance in time. For example, where the hardware modules comprise ageneral-purpose processor configured using software, the general-purposeprocessor may be configured as respective different hardware modules atdifferent times. Software may accordingly configure a processor, forexample, to constitute a particular hardware module at one instance oftime and to constitute a different hardware module at a differentinstance of time.

Hardware and software modules may provide information to, and receiveinformation from, other hardware and/or software modules. Accordingly,the described hardware modules may be regarded as being communicativelycoupled. Where multiple of such hardware or software modules existcontemporaneously, communications may be achieved through signaltransmission (e.g., over appropriate circuits and buses) that connectthe hardware or software modules. In embodiments in which multiplehardware modules or software are configured or instantiated at differenttimes, communications between such hardware or software modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware or software moduleshave access. For example, one hardware or software module may perform anoperation and store the output of that operation in a memory device towhich it is communicatively coupled. A further hardware or softwaremodule may then, at a later time, access the memory device to retrieveand process the stored output. Hardware and software modules may alsoinitiate communications with input or output devices, and may operate ona resource (e.g., a collection of information).

The various operations of example functions and methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods or functions described herein may be at leastpartially processor-implemented. For example, at least some of thefunctions of a method may be performed by one or processors orprocessor-implemented hardware modules. The performance of certain ofthe functions may be distributed among the one or more processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of thefunctions may be performed by a group of computers (as examples ofmachines including processors), these operations being accessible via anetwork (e.g., the Internet) and via one or more appropriate interfaces(e.g., application program interfaces (APIs)).

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Still further, the figures depict preferred embodiments of an examplesystem 100 and methods for purposes of illustration only. One ofordinary skill in the art will readily recognize from the followingdiscussion that alternative embodiments of the structures and methodsillustrated herein may be employed without departing from the principlesdescribed herein.

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative structural and functional designs for asystem and method for generating data regarding a vehicle crash. Thus,while particular embodiments and applications have been illustrated anddescribed, it is to be understood that the disclosed embodiments are notlimited to the precise construction and components disclosed herein.Various modifications, changes and variations, which will be apparent tothose skilled in the art, may be made in the arrangement, operation anddetails of the method and apparatus disclosed herein without departingfrom the spirit and scope defined in the appended claims.

To the extent that any meaning or definition of a term in this documentconflicts with any meaning or definition of the same term in a documentincorporated by reference, the meaning or definition assigned to thatterm in this document shall govern. Although the text sets forth adetailed description of numerous different embodiments, it should beunderstood that the legal scope of the description is defined by thewords of the claims set forth at the end of this patent. The detaileddescription is to be construed as exemplary only and does not describeevery possible embodiment since describing every possible embodimentwould be impractical, if not impossible. Numerous alternativeembodiments could be implemented, using either current technology ortechnology developed after the filing date of this patent, which wouldstill fall within the scope of the claims. While particular embodimentsof the present invention have been illustrated and described, it wouldbe obvious to those skilled in the art that various other changes andmodifications can be made without departing from the spirit and scope ofthe invention. It is therefore intended to cover in the appended claimsall such changes and modifications that are within the scope of thisinvention.

What is claimed is:
 1. A computer-implemented method for generating dataregarding a vehicle crash, the method comprising: receiving, using oneor more processors of a mobile computing device within a vehicle,initial sensor data indicating that a vehicle crash has occurred, andadditional sensor data for a first amount of time; and generating, usingthe one or more processors, combined sensor data that includes firstsensor data corresponding to a period of time before the crash of thevehicle and second sensor data corresponding to a period of time afterthe crash of the vehicle.
 2. The computer-implemented method of claim 1,further comprising: storing, using the one or more processors, theinitial sensor data in a buffer of the mobile computing device; andcausing, using the one or more processors, at least a portion of theinitial sensor data stored in the buffer to be stored in additional datastorage of the mobile computing device when it is determined that theinitial sensor data includes sensor data indicating that the vehiclecrash has occurred.
 3. The computer-implemented method of claim 2, thebuffer including storage capacity for one of a first amount of sensordata or a lower of a second amount of sensor data or an amount of sensordata that corresponds to a second amount of time.
 4. Thecomputer-implemented method of claim 2, the at least the portion of theinitial sensor data stored in the buffer including a first portion ofthe initial sensor data stored in the buffer, the buffer being afirst-in first-out (FIFO) buffer, the method further comprisingremoving, using the one or more processors, a second portion of theinitial sensor data stored in the buffer from the buffer when an amountof the initial sensor data exceeds a storage capacity of the buffer. 5.The computer-implemented method of claim 2, the method furthercomprising storing, using the one or more processors, the additionalsensor data in the buffer, wherein generating the combined sensor dataincludes causing, using the one or more processors, the additionalsensor data stored in the buffer to be stored in the additional datastorage of the mobile computing device after the first amount of time togenerate the combined sensor data including the first sensor datacorresponding to the period of time before the crash of the vehicle andthe second sensor data corresponding to the period of time after thecrash of the vehicle.
 6. The computer-implemented method of claim 1, thefirst amount of time being a predetermined amount of time correspondingto an expected duration of the crash of the vehicle.
 7. Thecomputer-implemented method of claim 1, further comprising: correlating,using the one or more processors, the combined sensor data withidentifying data associated with the mobile computing device; and makingavailable, using the one or more processors, the correlated combinedsensor data and identifying data associated with the mobile computingdevice to an insurance provider, the insurance provider providinginsurance coverage associated with the vehicle to a user of the mobilecomputing device.
 8. A computing device for generating data regarding avehicle crash, the computing device comprising: one or more processors;and one or more memories coupled to the one or more processors, the oneor more memories including non-transitory computer executableinstructions stored therein that, when executed by the one or moreprocessors, cause the one or more processors to: receive initial sensordata via the one or more processors indicating that a vehicle crash hasoccurred, and additional sensor data for a first amount of time; andgenerate, using the one or more processors, combined sensor data thatincludes first sensor data corresponding to a period of time before thecrash of the vehicle and second sensor data corresponding to a period oftime after the crash of the vehicle.
 9. The computing device of claim 8,the one or more memories further including non-transitory computerexecutable instructions that when executed cause the one or moreprocessors to: store the initial sensor data in a buffer of a mobilecomputing device; and cause at least a portion of the initial sensordata stored in the buffer to be stored in additional data storage of themobile computing device when it is determined that the initial sensordata includes sensor data indicating that the crash of the vehicle hasoccurred.
 10. The computing device of claim 9, the buffer includingstorage capacity for one of a first amount of sensor data or a lower ofa second amount of sensor data or an amount of sensor data thatcorresponds to a second amount of time.
 11. The computing device ofclaim 9, the at least the portion of the initial sensor data stored inthe buffer including a first portion of the initial sensor data storedin the buffer, the buffer being a first-in first-out (FIFO) buffer, theone or more memories further including non-transitory computerexecutable instructions that when executed cause the one or moreprocessors to remove a second portion of the initial sensor data storedin the buffer from the buffer when an amount of the initial sensor dataexceeds a storage capacity of the buffer.
 12. The computing device ofclaim 9, the one or more memories further including non-transitorycomputer executable instructions that when executed cause the one ormore processors to store the additional sensor data in the buffer,wherein the non-transitory computer executable instructions that whenexecuted cause the one or more processors to generate the combinedsensor data include non-transitory computer executable instructions thatwhen executed cause the one or more processors to cause the additionalsensor data stored in the buffer to be stored in the additional datastorage of the mobile computing device after the first amount of time togenerate the combined sensor data including the first sensor datacorresponding to the period of time before the crash of the vehicle andthe second sensor data corresponding to the period of time after thecrash of the vehicle.
 13. The computing device of claim 8, the firstamount of time being a predetermined amount of time corresponding to anexpected duration of the crash of the vehicle.
 14. The computing deviceof claim 8, the one or more memories further including non-transitorycomputer executable instructions that when executed cause the one ormore processors to: correlate the combined sensor data with identifyingdata associated with a mobile computing device; and make available thecorrelated combined sensor data and identifying data associated with themobile computing device to an insurance provider, the insurance providerproviding insurance coverage associated with the vehicle to a user ofthe mobile computing device.
 15. A computer readable storage mediumcomprising non-transitory computer readable instructions stored thereonfor generating data regarding a vehicle crash, wherein the instructionswhen executed on one or more processors cause the one or more processorsto: receive initial sensor data via the one or more processorsindicating that a vehicle crash has occurred, and additional sensor datafor a first amount of time; and generate, using the one or moreprocessors, combined sensor data that includes first sensor datacorresponding to a period of time before the crash of the vehicle andsecond sensor data corresponding to a period of time after the crash ofthe vehicle.
 16. The computer readable storage medium of claim 15,further comprising non-transitory computer readable instructions storedthereon that when executed cause the one or more processors to: storethe initial sensor data in a buffer of a mobile computing device; andcause at least a portion of the initial sensor data stored in the bufferto be stored in additional data storage of the mobile computing devicewhen it is determined that the initial sensor data includes sensor dataindicating that the crash of the vehicle has occurred.
 17. The computerreadable storage medium of claim 16, the at least the portion of theinitial sensor data stored in the buffer including a first portion ofthe initial sensor data stored in the buffer, the buffer being afirst-in first-out (FIFO) buffer, the computer readable storage mediumfurther comprising non-transitory computer readable instructions storedthereon that when executed cause the one or more processors to remove asecond portion of the initial sensor data stored in the buffer from thebuffer when an amount of the initial sensor data exceeds a storagecapacity of the buffer.
 18. The computer readable storage medium ofclaim 16, further comprising non-transitory computer readableinstructions stored thereon that when executed cause the one or moreprocessors to store the additional sensor data in the buffer, whereinthe non-transitory computer readable instructions that when executedcause the one or more processors to generate the combined sensor datainclude non-transitory computer readable instructions that when executedcause the one or more processors to cause the additional sensor datastored in the buffer to be stored in the additional data storage of themobile computing device after the first amount of time to generate thecombined sensor data including the first sensor data corresponding tothe period of time before the crash of the vehicle and the second sensordata corresponding to the period of time after the crash of the vehicle.19. The computer readable storage medium of claim 15, the first amountof time being a predetermined amount of time corresponding to anexpected duration of the crash of the vehicle.
 20. The computer readablestorage medium of claim 15, further comprising non-transitory computerreadable instructions stored thereon that when executed cause the one ormore processors to: correlate the combined sensor data with identifyingdata associated with a mobile computing device; and make available thecorrelated combined sensor data and identifying data associated with themobile computing device to an insurance provider, the insurance providerproviding insurance coverage associated with the vehicle to a user ofthe mobile computing device.